FHIR © HL7.org  |  Server Home  |  FHIR Server FHIR Server 3.4.11  |  FHIR Version n/a  User: [n/a]

Resource Requirements/FHIR Server from package hl7.ehrs.ehrsfmr21#current (31 ms)

Package hl7.ehrs.ehrsfmr21
Type Requirements
Id Id
FHIR Version R5
Source http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-RI.1.1.6.html
Url http://hl7.org/ehrs/Requirements/EHRSFMR2.1-RI.1.1.6
Version 2.1.0
Status active
Date 2024-11-26T16:30:50+00:00
Name RI_1_1_6_Report__Output__Record_Lifecycle_Event
Title RI.1.1.6 Report (Output) Record Lifecycle Event (Function)
Experimental False
Realm uv
Authority hl7
Description Report (Output) Record Entries (1 or more instances)
Purpose Occurs when an agent causes the system to produce and deliver record entry content in a particular form and manner. Reference: ISO 21089-2018, Section 15.6.

Resources that use this resource

No resources found


Resources that this resource uses

No resources found



Narrative

Note: links and images are rebased to the (stated) source

Statement N:

Report (Output) Record Entries (1 or more instances)

Description I:

Occurs when an agent causes the system to produce and deliver record entry content in a particular form and manner.

Reference: ISO 21089-2018, Section 15.6.

Criteria N:
RI.1.1.6#01 SHOULD

The system SHOULD provide the ability to render Record Entry content (e.g., as a report) retaining original, unaltered content and signature bindings, Action and Record Entry provenance and metadata.

RI.1.1.6#02 SHALL

The system SHALL provide the ability to render Record Entry extracts, including content, context, provenance and metadata.

RI.1.1.6#03 SHALL

The system SHALL provide the ability to capture the identity of the patient or the individual subject who is the target of Record Entry content that is presented/reported.

RI.1.1.6#04 dependent conditional SHOULD

IF the identity of a specific recipient has been stored, THEN the system SHOULD render protected Record Entry content based on established permissions and according to scope of practice, organizational policy, and/or jurisdictional law.

RI.1.1.6#05 conditional SHOULD

IF known and explicit as to Record Entry content being output/reported, THEN the system SHOULD transmit corresponding authorizations and patient consent permissions.

RI.1.1.6#06 SHALL

The system SHALL conform to function [[TI.1.6]] (Secure Data Exchange).

RI.1.1.6#07 SHALL

The system SHALL provide the ability to extract Record Entry content prior to output/report, conforming to function [[RI.1.1.13]] (Extract Record Entry Content).

RI.1.1.6#08 SHALL

The system SHALL provide the ability to de-identify Record Entry content prior to output/report, conforming to function [[RI.1.1.10]] (De-Identify Record Entries).

RI.1.1.6#09 dependent SHALL

The system SHALL provide the ability to render updates (new versions) of Record Entry Content to known recipients of prior versions of that Record Entry Content according to scope of practice, organizational policy, and/or jurisdictional law.


Source

{
  "resourceType" : "Requirements",
  "id" : "EHRSFMR2.1-RI.1.1.6",
  "meta" : {
    "profile" : [
      "http://hl7.org/ehrs/StructureDefinition/FMFunction"
    ]
  },
  "text" : {
    "status" : "extensions",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Report (Output) Record Entries (1 or more instances)</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>Occurs when an agent causes the system to produce and deliver record entry content in a particular form and manner.</p>\n<p>Reference: ISO 21089-2018, Section 15.6.</p>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>RI.1.1.6#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render Record Entry content (e.g., as a report) retaining original, unaltered content and signature bindings, Action and Record Entry provenance and metadata.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>RI.1.1.6#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to render Record Entry extracts, including content, context, provenance and metadata.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>RI.1.1.6#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to capture the identity of the patient or the individual subject who is the target of Record Entry content that is presented/reported.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>RI.1.1.6#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n <i>conditional</i>\n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>IF the identity of a specific recipient has been stored, THEN the system SHOULD render protected Record Entry content based on established permissions and according to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>RI.1.1.6#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n <i>conditional</i>\n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>IF known and explicit as to Record Entry content being output/reported, THEN the system SHOULD transmit corresponding authorizations and patient consent permissions.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>RI.1.1.6#06</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL conform to function [[TI.1.6]] (Secure Data Exchange).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>RI.1.1.6#07</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to extract Record Entry content prior to output/report, conforming to function [[RI.1.1.13]] (Extract Record Entry Content).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>RI.1.1.6#08</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to de-identify Record Entry content prior to output/report, conforming to function [[RI.1.1.10]] (De-Identify Record Entries).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>RI.1.1.6#09</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to render updates (new versions) of Record Entry Content to known recipients of prior versions of that Record Entry Content according to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
  },
  "url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-RI.1.1.6",
  "version" : "2.1.0",
  "name" : "RI_1_1_6_Report__Output__Record_Lifecycle_Event",
  "title" : "RI.1.1.6 Report (Output) Record Lifecycle Event (Function)",
  "status" : "active",
  "date" : "2024-11-26T16:30:50+00:00",
  "publisher" : "EHR WG",
  "contact" : [
    {
      "telecom" : [
        {
          "system" : "url",
          "value" : "http://www.hl7.org/Special/committees/ehr"
        }
      ]
    }
  ],
  "description" : "Report (Output) Record Entries (1 or more instances)",
  "jurisdiction" : [
    {
      "coding" : [
        {
          "system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code" : "001",
          "display" : "World"
        }
      ]
    }
  ],
  "purpose" : "Occurs when an agent causes the system to produce and deliver record entry content in a particular form and manner. \n\nReference: ISO 21089-2018, Section 15.6.",
  "statement" : [
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "EHRSFMR2.1-RI.1.1.6-01",
      "label" : "RI.1.1.6#01",
      "conformance" : [
        "SHOULD"
      ],
      "conditionality" : false,
      "requirement" : "The system SHOULD provide the ability to render Record Entry content (e.g., as a report) retaining original, unaltered content and signature bindings, Action and Record Entry provenance and metadata."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "EHRSFMR2.1-RI.1.1.6-02",
      "label" : "RI.1.1.6#02",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : false,
      "requirement" : "The system SHALL provide the ability to render Record Entry extracts, including content, context, provenance and metadata."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "EHRSFMR2.1-RI.1.1.6-03",
      "label" : "RI.1.1.6#03",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : false,
      "requirement" : "The system SHALL provide the ability to capture the identity of the patient or the individual subject who is the target of Record Entry content that is presented/reported."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : true
        }
      ],
      "key" : "EHRSFMR2.1-RI.1.1.6-04",
      "label" : "RI.1.1.6#04",
      "conformance" : [
        "SHOULD"
      ],
      "conditionality" : true,
      "requirement" : "IF the identity of a specific recipient has been stored, THEN the system SHOULD render protected Record Entry content based on established permissions and according to scope of practice, organizational policy, and/or jurisdictional law."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "EHRSFMR2.1-RI.1.1.6-05",
      "label" : "RI.1.1.6#05",
      "conformance" : [
        "SHOULD"
      ],
      "conditionality" : true,
      "requirement" : "IF known and explicit as to Record Entry content being output/reported, THEN the system SHOULD transmit corresponding authorizations and patient consent permissions."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "EHRSFMR2.1-RI.1.1.6-06",
      "label" : "RI.1.1.6#06",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : false,
      "requirement" : "The system SHALL conform to function [[TI.1.6]] (Secure Data Exchange)."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "EHRSFMR2.1-RI.1.1.6-07",
      "label" : "RI.1.1.6#07",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : false,
      "requirement" : "The system SHALL provide the ability to extract Record Entry content prior to output/report, conforming to function [[RI.1.1.13]] (Extract Record Entry Content)."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "EHRSFMR2.1-RI.1.1.6-08",
      "label" : "RI.1.1.6#08",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : false,
      "requirement" : "The system SHALL provide the ability to de-identify Record Entry content prior to output/report, conforming to function [[RI.1.1.10]] (De-Identify Record Entries)."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : true
        }
      ],
      "key" : "EHRSFMR2.1-RI.1.1.6-09",
      "label" : "RI.1.1.6#09",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : false,
      "requirement" : "The system SHALL provide the ability to render updates (new versions) of Record Entry Content to known recipients of prior versions of that Record Entry Content according to scope of practice, organizational policy, and/or jurisdictional law."
    }
  ]
}

XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.